Skip to content

chore: Configure Renovate#27

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#27
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 1, 2026

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • .devcontainer/devcontainer.json (devcontainer)
  • Dockerfile (dockerfile)
  • .github/workflows/lint.yml (github-actions)
  • .github/workflows/publish.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • go.mod (gomod)
  • config/agent/kustomization.yaml (kustomize)
  • config/manager/kustomization.yaml (kustomize)
  • config/tools/cert-manager/kustomization.yaml (kustomize)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 18 Pull Requests:

fix(deps): update module github.com/docker/docker to v28.5.2+incompatible
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-docker-docker-28.x
  • Merge into: main
  • Upgrade github.com/docker/docker to v28.5.2+incompatible
fix(deps): update module github.com/miekg/dns to v1.1.72
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-miekg-dns-1.x
  • Merge into: main
  • Upgrade github.com/miekg/dns to v1.1.72
fix(deps): update module github.com/projectdiscovery/dnsx to v1.2.3
chore(deps): update datum-cloud/actions action to v1.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/datum-cloud-actions-1.x
  • Merge into: main
  • Upgrade datum-cloud/actions to v1.9.0
chore(deps): update golang docker tag to v1.26
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: main
  • Upgrade golang to 1.26
chore(deps): update helm release cert-manager to v1.19.4
  • Schedule: ["at any time"]
  • Branch name: renovate/cert-manager-1.x
  • Merge into: main
  • Upgrade cert-manager to d0c202f57b8653eb957fb5b2f9472c1b11cf6b51acc5c777e4b824f7b5a9ea87
chore(deps): update helm release cert-manager-csi-driver to v0.12.1
  • Schedule: ["at any time"]
  • Branch name: renovate/cert-manager-csi-driver-0.x
  • Merge into: main
  • Upgrade cert-manager-csi-driver to 016638d69b5a3befba1bcaed2d7209d9a83c433424cdee15babfcebbece5bd86
fix(deps): update kubernetes packages to v0.35.2
fix(deps): update module github.com/onsi/ginkgo/v2 to v2.28.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-onsi-ginkgo-v2-2.x
  • Merge into: main
  • Upgrade github.com/onsi/ginkgo/v2 to v2.28.1
fix(deps): update module github.com/onsi/gomega to v1.39.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-onsi-gomega-1.x
  • Merge into: main
  • Upgrade github.com/onsi/gomega to v1.39.1
fix(deps): update module go.datum.net/network-services-operator to v0.17.0
fix(deps): update module go.miloapis.com/milo to v0.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/go.miloapis.com-milo-0.x
  • Merge into: main
  • Upgrade go.miloapis.com/milo to v0.19.1
fix(deps): update module golang.org/x/sync to v0.19.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-sync-0.x
  • Merge into: main
  • Upgrade golang.org/x/sync to v0.19.0
fix(deps): update module sigs.k8s.io/controller-runtime to v0.23.1
  • Schedule: ["at any time"]
  • Branch name: renovate/sigs.k8s.io-controller-runtime-0.x
  • Merge into: main
  • Upgrade sigs.k8s.io/controller-runtime to v0.23.1
fix(deps): update module sigs.k8s.io/multicluster-runtime to v0.23.1
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-go action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-go-6.x
  • Merge into: main
  • Upgrade actions/setup-go to v6
chore(deps): update golangci/golangci-lint-action action to v9

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

@cla-assistant
Copy link

cla-assistant bot commented Mar 1, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants